Documentation Doesn’t Confirm a Purchase. It Authorizes the Next Step.
On a project or in a regulated plant, a document set isn’t a formality that trails behind the physical goods — it’s what allows the next step to happen. Inspection can’t sign off without it. Goods-inward can’t clear a delivery without it. In many contracts, payment milestones are explicitly tied to it. Treat documentation as paperwork, and it becomes the thing everyone chases after the fact. Treat it as execution control, and it becomes something specified up front, at RFQ stage, like any other requirement.
Nowhere is this more visible than with material test certificates. A missing or wrong-type MTC is one of the most common — and most avoidable — causes of a delayed inspection or a held-up dispatch on an industrial project.
What a Complete Documentation Set Actually Contains
Depending on the category and the project’s requirements, a complete document set for an industrial delivery can include:
- Material test certificates (MTCs) — evidence of the material’s properties and conformity, in the certificate type the order specifies.
- Packing lists — confirming what’s physically in the shipment against what was ordered.
- Vendor data books — the compiled technical and quality documentation for equipment or assemblies, often a contractual deliverable in its own right on EPC projects.
- Inspection and test reports — records of any inspection carried out before dispatch, including third-party inspection where specified.
- Compliance declarations — statements of conformity to a specified standard or code, where applicable.
Each of these gates something downstream. A vendor data book gates project handover. A packing list gates goods-inward reconciliation. An MTC very often gates inspection sign-off and, from there, payment.
Material Test Certificates: What EN 10204 Actually Specifies
“MTC” is used loosely in industry conversation, but the certificate types that back it up are defined precisely by EN 10204, the standard covering inspection documents for metallic products. The four types differ on two things: whether the certificate carries test results at all, and how independent the party validating it is from the manufacturer’s own production line. Getting this distinction right matters, because each type implies a different level of assurance — and specifying the wrong one is a common, costly RFQ mistake.
Type 2.1 — Declaration of compliance with the order
Issued by the manufacturer. States that the supplied product complies with the order’s requirements. It does not include test results. This is the lightest-weight document in the standard — a statement, not evidence.
Type 2.2 — Test report
Also issued by the manufacturer, and it does include test results — but from non-specific inspection. In practice, that means the test results come from the manufacturer’s routine testing on the same type of product, not necessarily from tests performed on the specific batch or lot actually being supplied. It’s evidence, but not batch-traceable evidence.
Type 3.1 — Inspection certificate, manufacturer-validated
Based on specific inspection — meaning the tests are carried out on the actual product (or samples from the actual batch/lot) being supplied, so the results are traceable to what you’re receiving. Critically, a 3.1 certificate is validated by the manufacturer’s authorized inspection representative, who is organizationally independent of the production department — not simply signed off by the production line itself. This is what most industrial buyers mean when they ask for an “MTC” on a piping, structural steel, or fastener order.
Type 3.2 — Inspection certificate, jointly validated
Also based on specific inspection, but with a further layer of independence: the certificate is validated both by the manufacturer’s own independent inspection representative and by an inspector independent of the manufacturer entirely — either the purchaser’s own designated inspector or an inspector nominated under official/regulatory rules (for example, on statutory or third-party-witnessed equipment). This is the highest level of independent assurance in the standard, and it’s typically reserved for safety-critical or regulated equipment where the specification calls for third-party witness.
The distinction that matters most for an RFQ: 2.1 and 2.2 are entirely manufacturer-issued, with no independent validation. 3.1 and 3.2 are both based on specific, traceable inspection — the difference between them is whether one independent party validates it (3.1) or two (3.2). If your project specification calls for a 3.1 and a vendor supplies a 2.2, that is not a paperwork technicality — it is a different, lower level of assurance than what was specified, and it’s exactly the kind of gap that stops an inspection cold.
How Missing or Wrong-Type MTCs Delay Inspection and Dispatch
A shipment that arrives physically complete but without the correct certificate type typically can’t clear inspection, because the inspector has no traceable evidence that the product meets the specified requirement, regardless of how it looks. That holds up goods-inward, which holds up whatever the material was needed for, which — on a project with a fixed site schedule — can hold up a milestone that has nothing to do with the material itself. The fix at that point is slow: chasing the manufacturer for a retroactive certificate, or in the worst case, re-inspection or rejection.
The avoidable version of this problem is specifying the certificate type on the RFQ and PO in the first place, not discovering the requirement when the shipment is already in transit.
A Documentation-Gate Checklist Concept
Before issuing a PO for any documentation-sensitive category, confirm:
- [ ] The exact certificate type required (2.1, 2.2, 3.1, or 3.2) is stated on the RFQ and PO — not left to the vendor’s default.
- [ ] Any third-party or purchaser-witnessed inspection requirement (relevant to a 3.2) is flagged before manufacturing starts, not after.
- [ ] Packing lists and vendor data book requirements, where applicable, are specified alongside the material certificate requirement.
- [ ] Documentation is confirmed as a dispatch-readiness item — due with the shipment, not chased afterward.
- [ ] A single point of contact owns documentation completeness for the order, the same way someone owns price and delivery.
FAQ
What’s the difference between a 3.1 and a 3.2 certificate? Both are based on specific, traceable inspection of the actual product supplied. A 3.1 is validated by the manufacturer’s own inspection representative, who is independent of the production department. A 3.2 adds a second, fully independent validation — either the purchaser’s own inspector or an official/regulatory-nominated inspector — making it the higher level of assurance, typically required for safety-critical or statutory equipment.
Is a 2.2 test report the same as an MTC? Not in the sense most industrial buyers mean by “MTC.” A 2.2 report includes test results, but from non-specific (routine) inspection, not testing traceable to the exact batch supplied. When buyers ask for an MTC on structural, piping, or fastener orders, they usually mean a 3.1 certificate.
Why would a project ever need a 3.2 instead of a 3.1? When the specification, code, or contract requires independent verification beyond the manufacturer’s own quality system — typically for safety-critical, pressure-retaining, or statutory equipment where a purchaser’s or official inspector must witness or validate the inspection.
Build This Into Your Next RFQ
Download the Documentation-Gate Checklist and build certificate-type and inspection requirements into your RFQs and POs up front, before they become an inspection delay.
